Optimizing synchronization of content management servers

ABSTRACT

Optimizing synchronization of content management servers is described. A caching server receives a message pointing to a synchronization file that includes multiple content synchronization messages. The caching server downloads the synchronization file based on the message. The caching server identifies multiple contents for synchronization based on the multiple content synchronization messages. The caching server synchronizes the multiple contents via a connection to a content server.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This is a continuation of, and claims a benefit of priority under 35U.S.C. § 120 from, U.S. patent application Ser. No. 14/132,176 filedDec. 18, 2013, entitled “OPTIMIZING SYNCHRONIZATION OF CONTENTMANAGEMENT SERVERS,” which is fully incorporated by reference herein.

BACKGROUND

An enterprise content management system provides online access tocontent stored using digital technology, information formerly availableonly on paper, microfilm, or microfiche. An enterprise contentmanagement system generates new metadata about content as the content ischecked in and out. Information about how and when content is used canenable an enterprise content management system to generate newfiltering, routing and search pathways, and retention-rule decisions. Anenterprise content management system provides access to data about emailand instant messaging, which may be used in business decisions. Theaudit trail generated by an enterprise content management systemenhances document security, and provides metrics to help measureproductivity and identify efficiency.

An enterprise content management system provides integrated solutionsfor multiple departments and systems, as many documents may crossmultiple departments and affect multiple processes. For example,imaging, document management, and workflow can be combined in a customerservice department to enable customer service agents to better resolvecustomer inquiries. Likewise, an accounting department may accesssupplier invoices from an electronic resource management system, accesspurchase orders from an imaging system, and access contracts from adocument management system as part of an approval workflow. Similarly,an organization may present information via the World Wide Web, whichrequires managing web content.

BRIEF DESCRIPTION OF THE DRAWINGS

Advantages of the subject matter claimed will become apparent to thoseskilled in the art upon reading this description in conjunction with theaccompanying drawings, in which like reference numerals have been usedto designate like elements, and in which:

FIG. 1 is a block diagram illustrating an example hardware device inwhich the subject matter may be implemented;

FIG. 2 illustrates a block diagram of an example system for optimizingsynchronization of content management servers, under an embodiment; and

FIG. 3 is a flowchart that illustrates an example method for optimizingsynchronization of content management servers, under an embodiment.

DETAILED DESCRIPTION

An enterprise content management system's primary content server maycache content in multiple caching servers at distributed geographicallocations, which may be referred to as branch office caching servers.This enables client computers that are located closer to the multiplecaching servers to access the content faster than if all of the clientaccess requests were handled by the primary content server. Whenever newcontent is added into any of the content servers, the enterprise contentmanagement system synchronizes any changes to the content to the primarycontent server and/or all of the multiple caching servers so that thelatest content is available through any of the multiple caching servers.

Typically, a scheduler periodically generates synchronization messagesbased on any changes identified in content metadata stored by theprimary content server, generating a separate synchronization messagefor all of the new content to be synchronized. Generating a separatesynchronization message for each content update and sending them acrossa network to the messaging server for forwarding to all of the cachingservers is a very expensive operation. It utilizes a significant amountof network bandwidth and causing a significant load for the primarycontent server.

The primary content server generates a separate digital signature basedon the content updates and includes the separate digital signature inthe synchronization message for each content update to be synchronized.A messaging server forwards the synchronization messages, including theseparate digital signatures, to the corresponding caching servers. Eachof the multiple caching servers validates the separate digital signatureof each message and processes each of the separate digital signaturesseparately. When the number of synchronization messages is significantlylarge, generating the separate digital signatures and validating theseseparate digital signatures in both the caching servers and the primarycontent server can become an expensive operation for eachsynchronization message.

Each of the multiple caching servers makes a separate connection to theprimary content server for each synchronization message to requestsynchronization of the content based on the synchronization messages.Again, when the number of synchronization messages is significantlylarge, creating a separate connection for each synchronization messagemay also become an expensive operation. The content server validates theseparate digital signatures in each of the synchronization requests, andprocesses each of the separate digital signatures separately.

When a caching server that needs to be synchronized has been out ofoperation for a significant period of time, the primary content servercontinues generating synchronization messages for the caching server,including duplicate synchronization messages for the same contentupdates. As a result, the messaging server may become overloaded with alarge backlog of synchronization messages, which may cause performancerelated problems. Synchronization messages that the messaging serverdoes not process within a particular time period become expired, whichmay result in a messaging server becoming overloaded with a significantnumber of unprocessed messages. Furthermore, a caching server cannotdetermine whether a synchronization message is expired or not until thecaching server receives the synchronization message. This means that ifa scheduler generates 1,000 synchronization messages while the cachingserver is out of operation, then the caching server will receive all1,000 messages before determining that almost all of the 1,000synchronization messages are expired, thereby creating a significantperformance problem.

Embodiments herein enable optimizing synchronization of contentmanagement servers. A system receives a message pointing to asynchronization file that includes multiple content synchronizationmessages. For example, an optimizer tool receives a wrapper message thatpoints to a synchronization file of 10 content synchronization messages.The system downloads the synchronization file based on the message. Forexample, the optimizer tool downloads the synchronization file pointedto by the wrapper message. The system identifies multiple contents forsynchronization based on the multiple content synchronization messages.For example, a caching server parses the synchronization file toidentify the 10 content synchronization messages, which identify thecontent the caching server stores that should be synchronized. Thesystem synchronizes the multiple contents via a connection to a contentserver. For example, the optimizer tool makes a single connection to theprimary content server to synchronize the 10 content updatescorresponding to the 10 content synchronization messages, therebyconserving system resources by making fewer connections.

Prior to describing the subject matter in detail, an exemplary hardwaredevice in which the subject matter may be implemented shall first bedescribed. Those of ordinary skill in the art will appreciate that theelements illustrated in FIG. 1 may vary depending on the systemimplementation. With reference to FIG. 1, an exemplary system forimplementing the subject matter disclosed herein includes a hardwaredevice 100, including a processing unit 102, memory 104, storage 106,data entry module 108, display adapter 110, communication interface 112,and a bus 114 that couples elements 104-112 to the processing unit 102.

The bus 114 may comprise any type of bus architecture. Examples includea memory bus, a peripheral bus, a local bus, etc. The processing unit102 is an instruction execution machine, apparatus, or device and maycomprise a microprocessor, a digital signal processor, a graphicsprocessing unit, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), etc. The processing unit 102 maybe configured to execute program instructions stored in memory 104and/or storage 106 and/or received via data entry module 108.

The memory 104 may include read only memory (ROM) 116 and random accessmemory (RAM) 118. Memory 104 may be configured to store programinstructions and data during operation of device 100. In variousembodiments, memory 104 may include any of a variety of memorytechnologies such as static random access memory (SRAM) or dynamic RAM(DRAM), including variants such as dual data rate synchronous DRAM (DDRSDRAM), error correcting code synchronous DRAM (ECC SDRAM), or RAMBUSDRAM (RDRAM), for example. Memory 104 may also include nonvolatilememory technologies such as nonvolatile flash RAM (NVRAM) or ROM. Insome embodiments, it is contemplated that memory 104 may include acombination of technologies such as the foregoing, as well as othertechnologies not specifically mentioned. When the subject matter isimplemented in a computer system, a basic input/output system (BIOS)120, containing the basic routines that help to transfer informationbetween elements within the computer system, such as during start-up, isstored in ROM 116.

The storage 106 may include a flash memory data storage device forreading from and writing to flash memory, a hard disk drive for readingfrom and writing to a hard disk, a magnetic disk drive for reading fromor writing to a removable magnetic disk, and/or an optical disk drivefor reading from or writing to a removable optical disk such as a CDROM, DVD or other optical media. The drives and their associatedcomputer-readable media provide nonvolatile storage of computer readableinstructions, data structures, program modules and other data for thehardware device 100.

It is noted that the methods described herein can be embodied inexecutable instructions stored in a computer readable medium for use byor in connection with an instruction execution machine, apparatus, ordevice, such as a computer-based or processor-containing machine,apparatus, or device. It will be appreciated by those skilled in the artthat for some embodiments, other types of computer readable media may beused which can store data that is accessible by a computer, such asmagnetic cassettes, flash memory cards, digital video disks, Bernoullicartridges, RAM, ROM, and the like may also be used in the exemplaryoperating environment. As used here, a “computer-readable medium” caninclude one or more of any suitable media for storing the executableinstructions of a computer program in one or more of an electronic,magnetic, optical, and electromagnetic format, such that the instructionexecution machine, system, apparatus, or device can read (or fetch) theinstructions from the computer readable medium and execute theinstructions for carrying out the described methods. A non-exhaustivelist of conventional exemplary computer readable medium includes: aportable computer diskette; a RAM; a ROM; an erasable programmable readonly memory (EPROM or flash memory); optical storage devices, includinga portable compact disc (CD), a portable digital video disc (DVD), ahigh definition DVD (HD-DVD™) a BLU-RAY disc; and the like.

A number of program modules may be stored on the storage 106, ROM 116 orRAM 118, including an operating system 122, one or more applicationsprograms 124, program data 126, and other program modules 128. A usermay enter commands and information into the hardware device 100 throughdata entry module 108. Data entry module 108 may include mechanisms suchas a keyboard, a touch screen, a pointing device, etc. Other externalinput devices (not shown) are connected to the hardware device 100 viaexternal data entry interface 130. By way of example and not limitation,external input devices may include a microphone, joystick, game pad,satellite dish, scanner, or the like. In some embodiments, externalinput devices may include video or audio input devices such as a videocamera, a still camera, etc. Data entry module 108 may be configured toreceive input from one or more users of device 100 and to deliver suchinput to processing unit 102 and/or memory 104 via bus 114.

A display 132 is also connected to the bus 114 via display adapter 110.Display 132 may be configured to display output of device 100 to one ormore users. In some embodiments, a given device such as a touch screen,for example, may function as both data entry module 108 and display 132.External display devices may also be connected to the bus 114 viaexternal display interface 134. Other peripheral output devices, notshown, such as speakers and printers, may be connected to the hardwaredevice 100.

The hardware device 100 may operate in a networked environment usinglogical connections to one or more remote nodes (not shown) viacommunication interface 112. The remote node may be another computer, aserver, a router, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto the hardware device 100. The communication interface 112 mayinterface with a wireless network and/or a wired network. Examples ofwireless networks include, for example, a BLUETOOTH network, a wirelesspersonal area network, a wireless 802.11 local area network (LAN),and/or wireless telephony network (e.g., a cellular, PCS, or GSMnetwork). Examples of wired networks include, for example, a LAN, afiber optic network, a wired personal area network, a telephony network,and/or a wide area network (WAN). Such networking environments arecommonplace in intranets, the Internet, offices, enterprise-widecomputer networks and the like. In some embodiments, communicationinterface 112 may include logic configured to support direct memoryaccess (DMA) transfers between memory 104 and other devices.

In a networked environment, program modules depicted relative to thehardware device 100, or portions thereof, may be stored in a remotestorage device, such as, for example, on a server. It will beappreciated that other hardware and/or software to establish acommunications link between the hardware device 100 and other devicesmay be used.

It should be understood that the arrangement of hardware device 100illustrated in FIG. 1 is but one possible implementation and that otherarrangements are possible. It should also be understood that the varioussystem components (and means) defined by the claims, described below,and illustrated in the various block diagrams represent logicalcomponents that are configured to perform the functionality describedherein. For example, one or more of these system components (and means)can be realized, in whole or in part, by at least some of the componentsillustrated in the arrangement of hardware device 100.

In addition, while at least one of these components are implemented atleast partially as an electronic hardware component, and thereforeconstitutes a machine, the other components may be implemented insoftware, hardware, or a combination of software and hardware. Moreparticularly, at least one component defined by the claims isimplemented at least partially as an electronic hardware component, suchas an instruction execution machine (e.g., a processor-based orprocessor-containing machine) and/or as specialized circuits orcircuitry (e.g., discrete logic gates interconnected to perform aspecialized function), such as those illustrated in FIG. 1. Othercomponents may be implemented in software, hardware, or a combination ofsoftware and hardware. Moreover, some or all of these other componentsmay be combined, some may be omitted altogether, and additionalcomponents can be added while still achieving the functionalitydescribed herein. Thus, the subject matter described herein can beembodied in many different variations, and all such variations arecontemplated to be within the scope of what is claimed.

In the description that follows, the subject matter will be describedwith reference to acts and symbolic representations of operations thatare performed by one or more devices, unless indicated otherwise. Assuch, it will be understood that such acts and operations, which are attimes referred to as being computer-executed, include the manipulationby the processing unit of data in a structured form. This manipulationtransforms the data or maintains it at locations in the memory system ofthe computer, which reconfigures or otherwise alters the operation ofthe device in a manner well understood by those skilled in the art. Thedata structures where data is maintained are physical locations of thememory that have particular properties defined by the format of thedata. However, while the subject matter is being described in theforegoing context, it is not meant to be limiting as those of skill inthe art will appreciate that various of the acts and operationsdescribed hereinafter may also be implemented in hardware.

To facilitate an understanding of the subject matter described below,many aspects are described in terms of sequences of actions. At leastone of these aspects defined by the claims is performed by an electronichardware component. For example, it will be recognized that the variousactions can be performed by specialized circuits or circuitry, byprogram instructions being executed by one or more processors, or by acombination of both. The description herein of any sequence of actionsis not intended to imply that the specific order described forperforming that sequence must be followed. All methods described hereincan be performed in any suitable order unless otherwise indicated hereinor otherwise clearly contradicted by context. In an embodiment, thecomputer system 100 includes one or more methods for optimizingsynchronization of content management servers.

FIG. 2 illustrates a block diagram of a system that implementsoptimizing synchronization of content management servers, under anembodiment. As shown in FIG. 2, system 200 may illustrate a cloudcomputing environment in which data, applications, services, and otherresources are stored and delivered through shared data-centers andappear as a single point of access for the users. The system 200 mayalso represent any other type of distributed computer networkenvironment in which servers control the storage and distribution ofresources and services for different client users.

In an embodiment, the system 200 represents a cloud computing systemthat includes a client 202, and a first server 204, a second server 206,a third server 208, and a fourth server 210 that are provided by ahosting company. The client 202 and the servers 204-210 communicate viaa network 212. The first server 204 includes a first optimizer tool 214,and may be referred to as a first caching server 204, while the secondserver 206 includes a second optimizer tool 216, and may be referred toas a second caching server 206. The third server 208 includes anenterprise content management system 218, a first synchronization file220, and a second synchronization file 222, and may be referred to as aprimary content server 208, while the fourth server 210 may be referredto as a messaging server 210. The first server 204 accesses a firstdatabase 224, the second server 204 accesses a second database 226, andthe third server 208 accesses a third database 228. The databases224-228 may be referred to as Documentum® databases 224-228, which areprovided by EMC® Corporation. Alternatively, the databases 224-228 maybe some other database known in the art.

The first database 224 stores first objects 230, the second database 226stores second objects 232, and the third database 228 stores thirdobjects 234. The client 202 and the servers 204-210 may each besubstantially similar to the system 100 depicted in FIG. 1. AlthoughFIG. 2 depicts only one client 202, four servers 204-210, one network212, two optimizer tools 214-216, one enterprise content managementsystem 218, two synchronization files 220-222, three databases 224-228,and one of each of the system elements 230-234, the system 200 mayinclude any number of clients 202, servers 204-210, networks 212,optimizer tools 214-216, enterprise content management systems 218,synchronization files 220-222, databases 224-228, and each of the systemelements 230-234.

The primary content server 208 processes synchronization messagescollectively, which may be based on instructions from the firstoptimizer tool 214. This eliminates the need to send a separatesynchronization message to a caching server for each instance that ascheduler executes and identifies new content updates for the cachingserver. Processing synchronization messages collectively reducesconsumption of system resources. The primary content server 208 storeseach of the synchronization messages for the first caching server 204 inthe first synchronization file 220 and creates a first wrapper messagethat points to the first synchronization file 220 after a specifiednumber of synchronization messages are stored in the firstsynchronization file 220 or a specified amount of time has passed.Subsequently, the primary content server 208 sends the first wrappermessage to the messaging server 210, which forwards the first wrappermessage to the first caching server 204. Sending only a single wrappermessage to the messaging server 210 significantly reduces the amount ofmessages sent to the messaging server 210, thereby reducing the load onthe messaging server 210 and conserving system resources.

Similarly, the primary content server 208 stores each of thesynchronization messages for the second caching server 206 in the secondsynchronization file 222, and processes the second synchronization file222 in a manner similar to how the primary content server 208 processesthe first synchronization file 220, which may be based on instructionsfrom the second optimizer tool 216.

The system 200 receives a message pointing to a synchronization filethat includes multiple content synchronization messages. For example,the first optimizer tool 214 receives the first wrapper message thatpoints to the first synchronization file 220, which stores 10 contentsynchronization messages. Instead of receiving a separatesynchronization message from messaging servers for each content update,the first optimizer tool 214 receives only a single wrapper message,thereby conserving system resources by sending fewer messages. The firstsynchronization file 220 may be a simple text file which can be parsedto extract the synchronization messages. The first optimizer tool 214may determine whether a digital signature associated with the firstwrapper message is valid.

Further, instead of generating a separate digital signature for eachsynchronization message, the primary content server 208 generates asingle digital signature for the first synchronization file 220 thatstores multiple synchronization messages, which may be based oninstructions from the first optimizer tool 214. Generating fewer digitalsignatures conserves system resources. Since the primary content server208 generates a single digital signature for multiple synchronizationmessages, the primary content server 208 excludes content identifierswhen generating the digital signature, as the digital signature will nolonger have a one-to-one correspondence with content updates. The firstoptimizer tool 214 may also determine whether the first wrapper messageis expired.

In another example, the second optimizer tool 216 receives a secondwrapper message that points to the second synchronization file 222,which stores 100 content synchronization messages. To avoid a situationwhere the messaging server 210 becomes overloaded with 100 contentsynchronization messages for each caching server that is out ofoperation for a significant period of time, the messaging server 210stores only a single wrapper message for each caching server that is outof operation for a significant period of time, thereby reducing thepossibility of overloading the messaging server 210.

The system 200 downloads a synchronization file based on a message. Forexample, the first optimizer tool 214 downloads the firstsynchronization file 220 pointed to by the first wrapper message. Thefirst optimizer tool 214 may download the first synchronization file 220only if the single digital signature associated with the first wrappermessage is valid, thereby avoiding the need to verify the validity of aseparate digital signature for each synchronization message. Thisconserves system resources by verifying the validity of fewer digitalsignatures. In addition, the first optimizer tool 214 may download thefirst synchronization file 220 only if the timestamp for the firstwrapper message is not expired, rather than having to determine whethereach synchronization message is expired. Again, this conserves systemresources by determining whether fewer messages are expired. In anotherexample, the second optimizer tool 216 downloads the secondsynchronization file 222 pointed to by the second wrapper message.

The system 200 identifies multiple contents for synchronization based onmultiple content synchronization messages. For example, the firstcaching server 204 parses the first synchronization file 220 to identifythe 10 content synchronization messages, which identify the firstobjects 230 that the first caching server 204 stores which should besynchronized. In another example, the second caching server 206 parsesthe second synchronization file 222 to identify the 100 contentsynchronization messages, which identify the second objects 232 that thesecond caching server 206 stores which should be synchronized.

The system 200 synchronizes multiple contents via a single connection toa content server. For example, the first optimizer tool 214 makes asingle connection to the primary content server 208 for the firstcaching server 204 to synchronize the 10 content updates for the firstobjects 230 that the first caching server 204 stores which should besynchronized. The first optimizer tool 214 makes a single connection tosynchronize the multiple content updates instead of making a separateconnection to a primary content server for synchronizing each contentupdate. This will also conserve system resources by making fewerconnections.

The first optimizer tool 214 sends the single digital signaturepreviously received with the first wrapper message when requesting tosynchronize the 10 content updates for the first objects 230. This makesit unnecessary to send a separate digital signature when requesting tosynchronize each content update so that system sends fewer digitalsignatures. As a result, the primary content server 208 validates only asingle digital signature for the 10 content updates for the firstobjects 230 as opposed to validating a separate digital signature foreach content update.

In another example, the second optimizer tool 216 makes a singleconnection to the primary content server 208 for the second cachingserver 206 to synchronize the 100 content updates for the second objects232 that the second caching server 206 stores which should besynchronized. If synchronizing content fails at some point during thecontent synchronization process, a caching server can identify whichcontent still needs to be synchronized, and reestablish a connectionwith a primary content server, which does not need to validate thedigital signature that the caching server sent with the originalsynchronization request. For example, the synchronization process failsafter the primary content server 208 downloaded the first 4 contentupdates corresponding to the first 4 synchronization messages. Then thefirst caching server 204 reestablishes a connection with the primarycontent server 208, requests the last 6 content updates corresponding tothe last 6 synchronization messages, and the primary content server 208downloads the last 6 content updates corresponding to the last 6synchronization messages, without re-validating the digital signaturethat the first caching server 204 sent with the original synchronizationrequest.

The optimizer tools 214-216 conserve system resources by making fewerconnections, and by enabling fewer sending of messages, fewergenerations of digital signatures, fewer sending of digital signatures,fewer verifications of digital signatures, and fewer determinations ofwhether messages are expired. The optimizer tools 214-216 reduce theloads on the caching servers 204-206, the primary content server 208,and the messaging server 210.

FIG. 3 is a flowchart that illustrates a method for optimizingsynchronization of content management servers. Flowchart 300 illustratesmethod acts illustrated as flowchart blocks for certain steps involvedin and/or between the client 202 and/or the servers 204-210 of FIG. 2.In some example embodiments, the method illustrated by the flowchart 300may be executed by a single server, such as server 204.

A message is received pointing to a synchronization file that includesmultiple content synchronization messages, block 302. For example, thefirst optimizer tool 214 receives the first wrapper message that pointsto the first synchronization file 220, which stores 10 contentsynchronization messages.

A synchronization file is downloaded based on a message, block 304. Forexample, the first optimizer tool 214 downloads the firstsynchronization file 220 pointed to by the first wrapper message.

Multiple contents are identified for synchronization based on multiplecontent synchronization messages, block 306. For example, the firstcaching server 204 parses the first synchronization file 220 to identifythe 10 content synchronization messages, which identify the firstobjects 230 that the first caching server 204 stores which should besynchronized.

Multiple contents are synchronized via a connection to a content server,block 308. For example, the first optimizer tool 214 makes a singleconnection to the primary content server 208 for the first cachingserver 204 to synchronize the 10 content updates for the first objects230 that the first caching server 204 stores which should besynchronized.

Although FIG. 3 depicts the blocks 302-308 occurring in a specificorder, the blocks 302-308 may occur in another order. Embodiments hereinenable optimizing synchronization of content management servers. Theoptimizer tools 214-216 conserve system resources by making fewerconnections, and by enabling fewer sending of messages, fewergenerations of digital signatures, fewer sending of digital signatures,fewer verifications of digital signatures, and fewer determinations ofwhether messages are expired. The optimizer tools 214-216 reduce theloads on the caching servers 204-206, the primary content server 208,and the messaging server 210.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the subject matter (particularly in the context ofthe following claims) are to be construed to cover both the singular andthe plural, unless otherwise indicated herein or clearly contradicted bycontext. Recitation of ranges of values herein are merely intended toserve as a shorthand method of referring individually to each separatevalue falling within the range, unless otherwise indicated herein, andeach separate value is incorporated into the specification as if it wereindividually recited herein. Furthermore, the foregoing description isfor the purpose of illustration only, and not for the purpose oflimitation, as the scope of protection sought is defined by the claimsas set forth hereinafter together with any equivalents thereof entitledto. The use of any and all examples, or exemplary language (e.g., “suchas”) provided herein, is intended merely to better illustrate thesubject matter and does not pose a limitation on the scope of thesubject matter unless otherwise claimed. The use of the term “based on”and other like phrases indicating a condition for bringing about aresult, both in the claims and in the written description, is notintended to foreclose any other conditions that bring about that result.No language in the specification should be construed as indicating anynon-claimed element as essential to the practice of the invention asclaimed.

Preferred embodiments are described herein, including the best modeknown to the inventor for carrying out the claimed subject matter. Ofcourse, variations of those preferred embodiments will become apparentto those of ordinary skill in the art upon reading the foregoingdescription. The inventor expects skilled artisans to employ suchvariations as appropriate, and the inventor intends for the claimedsubject matter to be practiced otherwise than as specifically describedherein. Accordingly, this claimed subject matter includes allmodifications and equivalents of the subject matter recited in theclaims appended hereto as permitted by applicable law. Moreover, anycombination of the above-described elements in all possible variationsthereof is encompassed unless otherwise indicated herein or otherwiseclearly contradicted by context.

1. A system for optimizing synchronization of content managementservers, the system comprising: a processor-based application executedon a computer and configured to: receive, by a caching server, a wrappermessage pointing to a synchronization file comprising a plurality ofcontent synchronization messages, the wrapper message having acorresponding digital signature; verify, by the caching server, thedigital signature corresponding to the wrapper message; download, by thecaching server in response to verifying the digital signaturecorresponding to the wrapper message, the synchronization file pointedto by the wrapper message; identify, by the caching server, a pluralityof contents for synchronization based on the plurality of contentsynchronization messages; synchronize, by the caching server, theplurality of contents via a single connection to a content server. 2.The system of claim 1, wherein receiving the wrapper message comprisesdetermining whether the wrapper message is expired; and whereindownloading the synchronization file comprises downloading thesynchronization file in response to a determination that the wrappermessage is not expired.
 3. The system of claim 1, further comprising thecontent server, wherein the content server is configured to generate andstore the synchronization file, wherein in response to verifying thedigital signature corresponding to the wrapper message, the cachingserver is configured to download the synchronization file from thecontent server via the single connection.
 4. The system of claim 1,wherein the digital signature is generated based on data that excludesthe plurality of content synchronization messages.
 5. The system ofclaim 3, wherein the digital signature is generated based on data thatexcludes content identifiers of the plurality of contents.
 6. The systemof claim 1, wherein the caching server synchronizes the plurality ofcontents identified from the plurality of content synchronizationmessages based on the verifying of only the digital signaturecorresponding to the wrapper message.
 7. The system of claim 1, whereinat least some of the plurality of contents for synchronization issynchronized to the content server by another caching server.
 8. Acomputer-implemented method for optimizing synchronization of contentmanagement servers, the method comprising: receiving, by a cachingserver, a wrapper message pointing to a synchronization file comprisinga plurality of content synchronization messages, the wrapper messagehaving a corresponding digital signature; verifying, by the cachingserver, the digital signature corresponding to the wrapper message;downloading, by the caching server in response to verifying the digitalsignature corresponding to the wrapper message, the synchronization filepointed to by the wrapper message; identifying, by the caching server, aplurality of contents for synchronization based on the plurality ofcontent synchronization messages; synchronizing, by the caching server,the plurality of contents via a single connection to a content server.9. The computer-implemented method of claim 8, wherein receiving thewrapper message comprises determining whether the wrapper message isexpired; and wherein downloading the synchronization file comprisesdownloading the synchronization file in response to a determination thatthe wrapper message is not expired.
 10. The computer-implemented methodof claim 8, further comprising generating and storing, by the contentserver, the synchronization file, wherein in response to verifying thedigital signature corresponding to the wrapper message, the cachingserver downloads the synchronization file from the content server viathe single connection.
 11. The computer-implemented method of claim 8,wherein the digital signature is generated based on data that excludescontent identifiers of the plurality of contents.
 12. Thecomputer-implemented method of claim 8, wherein the digital signature isgenerated based on data that excludes the plurality of contentsynchronization messages.
 13. The computer-implemented method of claim8, wherein synchronizing the plurality of contents identified from theplurality of content synchronization messages is based on the verifyingof only the digital signature corresponding to the wrapper message. 14.A computer program product, comprising a non-transitorycomputer-readable medium having a computer-readable program codeembodied therein to be executed by one or more processors, the programcode including instructions to: receive, by a caching server, a wrappermessage pointing to a synchronization file comprising a plurality ofcontent synchronization messages, the wrapper message having acorresponding digital signature; verify, by the caching server, thedigital signature corresponding to the wrapper message; download, by thecaching server in response to verifying the digital signaturecorresponding to the wrapper message, the synchronization file pointedto by the wrapper message; identify, by the caching server, a pluralityof contents for synchronization based on the plurality of contentsynchronization messages; synchronize, by the caching server, theplurality of contents via a single connection to a content server. 15.The computer program product of claim 14, wherein receiving the wrappermessage comprises determining whether the wrapper message is expired;and wherein downloading the synchronization file comprises downloadingthe synchronization file in response to a determination that the wrappermessage is not expired.
 16. The computer program product of claim 14,further comprising wherein in response to verifying the digitalsignature corresponding to the wrapper message, the caching serverdownloads the synchronization file from the content server via thesingle connection, the synchronization file being generated and storedby the content server.
 17. The computer program product of claim 14,wherein the digital signature is generated based on data that excludescontent identifiers of the plurality of contents.
 18. The computerprogram product of claim 14, wherein the digital signature is generatedbased on data that excludes the plurality of content synchronizationmessages.
 19. The computer program product of claim 14, whereinsynchronizing the plurality of contents identified from the plurality ofcontent synchronization messages is based on the verifying of only thedigital signature corresponding to the wrapper message.
 20. The computerprogram product of claim 14, wherein at least some of the plurality ofcontents for synchronization is synchronized to the content server byanother caching server.